Re: [NTG-context] [overstrike] with different color?

2020-06-05 Thread Wolfgang Schuster
Henning Hraban Ramm schrieb am 03.06.2020 um 16:30: Am 03.06.2020 um 16:19 schrieb Floris van Manen : What is the preferred way to overstrike a text with a different color? This does not work: One \overstrike[color=red]{Two} Three \setupbar[color=red,rulethickness=1.4] % measurement in pt

Re: [NTG-context] [overstrike] with different color?

2020-06-05 Thread Henning Hraban Ramm
> Am 04.06.2020 um 20:00 schrieb Floris van Manen : > >> \setupbar[color=red,rulethickness=1.4] % measurement in pt > > the command also takes a parameter offset as well as dy. > I assume the offset will position the line higher / lower . > But I see no effect. > >

Re: [NTG-context] [overstrike] with different color?

2020-06-04 Thread Floris van Manen
On 03/06/2020 16:30, Henning Hraban Ramm wrote: > \setupbar[color=red,rulethickness=1.4] % measurement in pt the command also takes a parameter offset as well as dy. I assume the offset will position the line higher / lower . But I see no effect.

Re: [NTG-context] [overstrike] with different color?

2020-06-03 Thread Henning Hraban Ramm
> Am 03.06.2020 um 16:19 schrieb Floris van Manen : > > What is the preferred way to overstrike a text with a different color? > This does not work: > One \overstrike[color=red]{Two} Three \setupbar[color=red,rulethickness=1.4] % measurement in pt See also rules-m

[NTG-context] [overstrike] with different color?

2020-06-03 Thread Floris van Manen
What is the preferred way to overstrike a text with a different color? This does not work: One \overstrike[color=red]{Two} Three .F pEpkey.asc Description: application/pgp-keys ___ If your question is of interest

[NTG-context] microtype + \overstrike + libertine problem

2010-11-22 Thread Marco Pessotto
Hello there. I'm experience the following problem: with microtypography \overstrike plays weird. See the following minimal. I can't reproduce it with the latin modern fonts, so maybe it's a font specific issue. I've found a workaround and documented it on the wiki (just in case) http